Hey @michaelhatPIengineering !
This PR basically adds the filter below (for browser WebHID only):

function isValidXkeysUsage(device: HIDDevice): boolean {
	return !!device.collections.find(
		(collection) => collection.type === 1 && collection.usage === 1 && collection.usagePage === 12
	)
}

Does this filter look reasonable to you? Do you think we should go ahead and merge this fix right away or would you like to test it with various devices first? (I could prepare a test script for you)

it seems like the fix worked on Mac, but not on Windows

looks like collection.type === 0 for XKeys XK-80 on Windows

I have stripped out some of the conditions, and left it checking usagePage and vendorId.
It is validating the productId later, so I don't think it is necessary to do at this early stage, especially as the user prompt isnt doing a filter on productId.

I haven't added a writeLength check, as doing so requires digging deeply into multiple layers of arrays and objects and that makes me a little uneasy about the reliability of doing so. Although each of linux, macos and windows did produce what appeared to be the same data for it:

ok, I have added that check. The function now looks like:

function isValidXkeysUsage(device: HIDDevice): boolean {
	if (device.vendorId !== XKEYS_VENDOR_ID) return false

	return !!device.collections.find((collection) => {
		if (collection.usagePage !== 12) return false

		// Check the write-length of the device is > 20
		return !!collection.outputReports?.find((report) => !!report.items?.find((item) => item.reportCount ?? 0 > 20))
	})
}

I have tested that this new version still works on windows, macos and linux